COMMENT ⊗   VALID 00006 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	.DEVICE XGP
C00003 00003	←%3How to start WAITS
C00007 00004	%2FIXING THE SYSTEM:%1
C00011 00005	%2RELOADING:%1
C00018 00006	%2RESTARTING THE KA-10:%1
C00021 ENDMK
C⊗;
.DEVICE XGP
.!XGPCOMMANDS←"/PMAR=0";
.!XGPLFTMAR←216;
.PAGE FRAME 999 HIGH 80 WIDE
.AREA TEXT LINES 1 TO 999 CHARS 1 TO 80
.PLACE TEXT
.FONT 1 "BASL30";
.FONT 2 "BASI30";
.FONT 3 "BUCK75";
.FONT 4 "FIX25";
.FONT 5 "FIX13X";
.TURN ON "←{%α↓_#"
.AT "ffi" ⊂ IF THISFONT ≤ 2 THEN "≠"  ELSE "fαfαi" ⊃;
.AT "ffl" ⊂ IF THISFONT ≤ 2 THEN "α∞" ELSE "fαfαl" ⊃;
.AT "ff"  ⊂ IF THISFONT ≤ 2 THEN "≥"  ELSE "fαf" ⊃;
.AT "fi"  ⊂ IF THISFONT ≤ 2 THEN "α≡" ELSE "fαi" ⊃;
.AT "fl"  ⊂ IF THISFONT ≤ 2 THEN "∨"  ELSE "fαl" ⊃;
←%3How to start WAITS

%2FIND A WIZARD:%1

.BEGIN INDENT 5

Before you do anything, you should try to find a wizard.  Maybe there is
already one working on the problem -- if so, he will be very angry if you
disturb the machine.  Check in the 030 block of offices (ME 030d, MRC
030c) and then call REG's office (7-3236)(room 422).  If necessary, call a
wizard at home (but not in the middle of the night unless it is an
%2urgent%* problem, as defined below).  If you can't find one, a reasonable
thing to do is NOTHING!

Home phone numbers of wizards:
.BEGIN NOFILL; INDENT 0;

%4
Martin Frost (ME) (10am → 11pm) (9)329-9081 or (9)325-8507 or 21-192 (beeper)
Roy Hayes (ROY) (reasonable hours) (56)996-2965 (%2hardware problems only%*)
.END
.BEGIN INDENT 0;
[%1Do %2not%* use 7-4975 to call out on, since that is the number that a
wizard might be trying to call in on.  If it rings, %2answer it%*.]

%1For an %2urgent%* problem you can beep ME at %2any%* time, but it better
really be urgent.  A problem is %2urgent%* if it is continuing or
repeating, e.g., you can't reload, or a similar emergency.  %2A#plain system
crash doesn't count as urgent%*, unless you are unable to reload after following
the reloading instructions below.  Even wizards don't like being awakened in
the middle of the night.

To call by beeper, dial the 21-xxx number, wait for the beeping to stop,
and then %2describe the problem in 10 seconds or less%*.  Your message is
transmitted right then by radio to the beepee.
.END

Sometimes a wizard will dial up the CTY to fix things from home, (possibly
without your knowing it).  When this happens, he may need some local help
from you.  %2Stand by%1 in case he asks you to do something like check
status lights.

If you can't get in touch with a wizard, you'll have to fix it yourself.
After you fix it, make a note in the log with the date, time and description
of the failure (include any message typed out on the CTY).  %2Sign your
log note%1.
.END

**********************************************************************
.SKIP 1
%2FIXING THE SYSTEM:%1

.BEGIN INDENT 5
Most crashes are bug traps and will print a message followed by:

←%4FIND A WIZARD or type "$P".  $ means ESC.  YOU'RE IN DDT.%1

If it prints this, try typing [ESC] %4P%1 and a couple of [RETURN]s.  If
you get monitor dots, you're winning.  Type %4BEEP%1 and [RETURN] to tell
everybody the good news.  %2Don't forget to log the crash!%1

If after you type %4$P%1 the same thing happens, try %4$P%1 again.  If it
repeatedly happens, you'll have to reload.  Go to step 1 below.  Note that
an %4EXEC Page Fault%1 message cannot be continued by typing %4$P%1; the
page fault will just happen again.  This type of crash is one of the
easiest for a wizard to fix, and the bug will just happen again later if
you reload.

If after you type %4$P%1 the system hangs, %2leave the system alone until
you find a wizard%1.  This is especially true if it follows a disk hung
timeout.  Reloading will probably %2not%1 help.

If the system is printing many %4PARITY ERROR%1 messages, you will
have to reset the losing memory.  If you don't know how to do this,
find somebody who does; reloading the system won't help!  Sometimes
even resetting the memory won't help; in that case the memories have
to be reconfigured or fixed.  You should leave that for a wizard to do.

If the machine has powered itself off (ie, the console PDP-11 and power
lights are off), then an overtemp probably happened.  Get help.  Do
%2NOT%1 power the system back on unless a wizard tells you to do so!

If an obscure message like %4?10 CLKOP%1 or %4?10 TTI%1 was printed on
the CTY, a memory is probably losing (hung or powered off); you can try
the command %4MC%* and [RETURN] to see if that helps.

The message %4?10 CMD ERR%1 means that the wrong version of %4KLDCP%* is
loaded; see step 104 below.

If no message was printed, or some message which doesn't look like
the example above, you will have to reload.
.END

**********************************************************************
.SKIP 1
%2RELOADING:%1

.BEGIN INDENT 5
1.  If there has been a power failure, go to 100.

2.  Type %4↑X%1 (ie, hold down %4CTRL%1 and type %4X%1).  The response
should be %4KLDCP%1 (or else it may echo simply as %4↑X%*).  If the
command typed in the next step doesn't echo, try this step again; then if
typing the next step's command still doesn't seem to work, go to step 100.

3.  Type %4SP%* and [RETURN].  This stops the KL-10 and records useful
information, including the PC, on the CTY for later perusal by a wizard.
If this command gets you the message %4?UCODE HUNG%*, then type the
command %4ALL%* and [RETURN]; this logs a few lines of information
so a wizard can figure out how the microcode was hung.  In either case,
go on to step 4 next.

4.  Type %4DS%1 and [RETURN].  If you get the response %4DSKDMP%1 go to
step 5.  If you get the message %4DEPOSIT/EXAMINE ERROR IN DS%1 then
perform step 102 and repeat step 4.  Otherwise if %4DS%1 doesn't get you
%4DSKDMP%1, go to 100.

5.  Type %4WAITS%1 and [RETURN].  If the system reloads and starts you
are winning.  If the system doesn't start, you must get help.
If you reloaded KLDCP from dectape in step 100c, you now
may have to perform step 104.   %2Don't forget to log the crash!%1
.END

%2Don't come here unless directed by the steps above.%1

.BEGIN INDENT 5
100.  KLDCP is the PDP-11 console program.  It prompts with a
greater than sign: ">".  By typing carriage return you should be
able to get another prompt.  If so, KLDCP is running.  Go to step 101.

100a. Try restarting KLDCP: set 100004 in the
PDP-11 switches (switches 15 and 2 up, all the rest down); push
HALT/ENABLE down and then restore it;  push LOAD ADDRESS down and restore
it; press START.  KLDCP should respond with a prompt; if so, go to 101.

100b. Try restarting KLDCP again.  This time, set 100010 in the address
switches (bits 15 and 3 up).  If you get KLDCP to start this time,
you will also have to reload DSKDMP (later, in step 103); go to step 101.

100c. If neither restart works, KLDCP must be reloaded from
DECtape.  Note that this is an OLD VERSION of KLDCP.  The new version
will have to be loaded in step 104.
Make sure a DECtape labeled "KL10 bootstrap" is mounted on
a PDP-11 DECtape drive that is selected to unit 0 and is enabled for
"remote" (ie, computer) operation.  Press "LOAD DECTAPE" [located
above and to the left of the red "Emergency Power Off" button] and
hold it for at least a slow count to one.  The DECtape should spin and
eventually something like %4TCDP monitor%1 should be typed.  Type in
%4KLDCP%1 and [RETURN].  KLDCP should load and type a message - go to
step 101.  If you don't get to TCDP you might try pressing the LOAD
DECTAPE button again.  If you get to TCDP and the %4KLDCP%1 command
doesn't work, get help.

101.  If there's been a power failure you will have to reload the
KL10's microcode.  Type %4DT0 LR SU%1 to KLDCP and [RETURN].  If any
error messages are printed, get help.  Type#%4SW#37#600000%1 and
[RETURN].

102.  After loading the microcode, you must configure the memory
adapter by typing %4I X4%1 and [RETURN].  If the system is running
with reduced memory this is probably the wrong thing.

103.  Now try steps 4 and 5.  If the command %4DS%1 gives the message
%4LOAD DSKDMP - USE LD%1, then load the DSKDMP bootstrap program into the
PDP-11 by %4LD BOOT%1 and [RETURN].  If that doesn't work, either the
memory adapter is configured wrong (step 102) or a memory is losing.  Get
help.

104.  Reload the right version of KLDCP [after step 5 is successful].  If
you had to load KLDCP from DECtape in step 100c, then when the system
runs, the 11 may halt with messages such as %4?10 CMD ERR%1.  The correct
version of KLDCP must be loaded, but the system should be partially usable
anyway.  If the CTY is working (i.e., the console-11 is somewhat happy),
then you can just type %411LOAD%* on the CTY.  Otherwise,
a suitably privileged user must log in and incant either

.BEGIN SELECT 4; no fill; no just
	11LOAD

%1or%*

	RUN 11LOAD[KL,SYS]
	AGRONK
	KLDCP.L11[KL,SYS]
.END
.END

**********************************************************************
.SKIP 1
%2RESTARTING THE KA-10:%1

.BEGIN INDENT 5
These instructions are for restarting the KA-10, which is the
secondary processor.  They assume that the main timesharing system
itself is running; presumably you are reading this because you were
told to restart the KA-10 by an XGP spooling of yours.  As always,
make sure a wizard is not already working on it.

The KA-10 is the black computer (the KL-10 is blue).  Its console
panel should be about four feet to the left of this sheet.  It will
have a lot of lights and switches on it.

To %2restart%1 the KA, first check the KA's address switches to be sure
that they are set to 204.  If you don't know how to do this, don't worry
since its switches should always be set to 204.  In addition, if the KA
stopped with a memory stop make a log entry with details of the memory
lossage (the note on the KA console says how to do this).

Now, restart the KA by pressing the RESET button on the KA-10 console
panel, then pressing the START button.  You should get a message on the
teletype next to the KA saying something like %4KA10 RESTARTED%1.

If you don't get this message, or if it is followed by some other message
that looks like an error message, try reloading the KA-10 (%2not%1 the
regular system!!).

To %2reload%1 the KA, press the KA-10 RESET button again.  Go to the KL-10
CTY and type %4P2%1 and [RETURN].  When it finishes, press the START button
on the KA-10 console panel.  If it doesn't work now, get help.
.END

**********************************************************************
.SKIP 1
The PUB source for this file is %4HTSWTS.MRC[UP,DOC]%1.  Corrections
marked on this sheet will be noted therein.